Tokens for Create Entry
The Create Entry activity produces the following tokens.
Name | Description | Sample Syntax* |
---|---|---|
OutputEntry_Name | The name of the new entry. | %(CreateEntry_OutputEntry_Name) |
OutputEntry_Id | The Laserfiche ID number of the new entry. | %(CreateEntry_OutputEntry_Id) |
OutputEntry_Path | The folder path of the new entry. | %(CreateEntry_OutputEntry_Path) |
OutputEntry_FullPath | The folder path of the new entry, including the entry's name. | %(CreateEntry_OutputEntry_FullPath) |
OutputEntry_Repository | The repository the new entry is in. | %(CreateEntry_OutputEntry_Repository) |
OutputEntry_Server | The Laserfiche Server that contains the new entry. | %(CreateEntry_OutputEntry_Server) |
OutputEntry_Guid | The GUID (Globally Unique Identifier) of the new entry. | %(CreateEntry_OutputEntry_Guid) |
ParentEntry_Name | The name of the folder in which the new entry was created. | %(CreateEntry_ParentEntry_Name) |
ParentEntry_Id | The Laserfiche ID of the folder in which the new entry was created. | %(CreateEntry_ParentEntry_Id) |
ParentEntry_Path | The folder path of the folder in which the new entry was created. | %(CreateEntry_ParentEntry_Path) |
ParentEntry_FullPath | The folder path of the folder in which the new entry was created, including the folder's name. | %(CreateEntry_ParentEntry_FullPath) |
ParentEntry_Repository | The repository that contains the folder in which the new entry was created. | %(CreateEntry_ParentEntry_Repository) |
ParentEntry_Server | The Laserfiche Server that contains the folder in which the new entry was created. | %(CreateEntry_ParentEntry_Server) |
ParentEntry_Guid | The GUID (Globally Unique Identifier) of the folder in which the new entry was created. | %(CreateEntry_ParentEntry_Guid) |
Created Parent Folder | Whether the Create Entry activity created the folder in which the new entry was placed. This token can have one of two possible values: True or False. | %(CreateEntry_Created Parent Folder) |
*The "CreateEntry" portion of the syntax changes to match the activity's name as specified in the Activity Name property box. Note that all non-alphanumeric characters, except underscores, are removed from the name. For example, if you rename the activity New *Sales* Document, the syntax for the OutputEntry_Id token will be %(NewSalesDocument_OutputEntry_Id).